Bekkah is primary driver of her car. After using AutoMindr, Bekkah has after-market wipers installed on her car for better visibility. Bekkah is a secondary driver on her mom's car and her dad's SUV. Bekkah is buddies in AutoMindr with her mom and is mentored by her dad. Bekkah usually lives in her apartment near the university she attends, however, she still uses her parent's address sometimes. In June, Bekkah will be taking an internship out of state and plans to take her car with her. She will later return to her apartment.
Jeff is Bekkah's dad. He mentors Bekkah in AutoMindr and is also a user. He is secondary driver on Bekkah's car and his wife's car. He is primary driver on his SUV. He is buddies with his wife. Jeff customized his SUV to have larger wheels than what comes standard. Jeff prefers to go to Al's Garage primarily because he really likes the work that Tricia does there. Jeff would like to give Tricia a separate rating different than Al's Garage.
See 2.1 Profile for additional information regarding the profile information that needs to be stored and mapped to.
Tutorial History
AutoMindr needs to know what tutorials a driver opts into or out of. AutoMindr also needs to map a tutorial to maintenance and car status. For example, Bekkah's learns she needs new tires with a tutorial. The tutorial guides her into changing her car's status to needing new tires. Eventually, she gets new tires and this maintenance item needs to be logged and the vehicle's status needs to changes.
AutoMindr needs to store if a tutorial was or was not completed. Did user choose to ignore or attempt? At first, Bekkah was asked to check her tires but didn't have time. Later, Bekkah uses the tutorial. Jeff on the other hand, opts out of the tutorials. AutoMindr needs to store both the history and preferences.
The tutorial also need to map to what car status they might change (new tires for example). Status changes are usually also a maintenance action too.
Quiz History
AutoMindr gives quizzes. Quiz history needs to be stored so it can be viewed. This data might also be used to define user levels for example. Quizzes need to be mapped to the user taking them. The date and location is used to determine the most convienient time to offer quizzes to drivers.
User ID
Quiz Question ID (quiz questions are pulled from a quiz bank)
Completed (did user choose to ignore or attempt?)
User Score
Date/Time
Location
Vehicle
Profile
Unique Vehicle ID (mandatory)
Make/Model/Year ID
VIN
Customization IDs (these are IDs to the Vehicle Parts Knowledge base of things like custom wheels).
Primary driver ID
Secondary drivers IDs
common car locations (must have ability to store multiple locations like home, school, and work parking).
preferred gas stations (multiple gas stations)
Status and Maintenance History
Status data and Maintenance data may be duplicated in the list below. This data may be combined in the backend. What is important though is that he car's current status must be accessible quickly and easily so AutoMindr can be intelligent enough to pick the right tutorials, quizzes, maintenance-action items (nag prompts), and so on. It is also important that the driver, mentor, or service professional be able to review the maintenance history. This history may be reviewed in whole or only one part of the history would be reviewed. For example, someone may just want to review the history of the transmission fluid.
Status
Ability to indicate if particular maintenance item dictates current status of vehicle.
Maintenance-action ID
Each status entry includes a maintenance-type ID (corresponds to type such as tire tread)
Examples of status types are: mileage, tire pressure status, tire tread status, tire rotation status, fluid levels, belt status, hose status.
Date of last status change (helpful when weather can affect status, such as winter wipers)
Current Location where last status change was entered (helpful when location can affect status such as urban, rural, desert climate, temperate climate, hilly, and so on).
Flag to nag with location and time history of previous nags.
Maintenance History
User ID who purchased maintenance
maintenance-type ID (corresponds to type such as tire tread)
Vehicle ID
location
Service Center ID
User ID who performed maintenance
cost
rating of service center and/or mechanic or a way to map to this data from the service center's data.
may want to flag if particular maintenance item defines current status
rating
optional comment
flag to nag for rating
Knowledge of Vehicle Makes and Models
This data does not necessarily need to be stored in AutoMindr, but AutoMindr will need access this data. This data includes information that would come from a manual for a particular make, model, year, and class (for example 2002 Oldsmobile Alero GX). If this data is stored in AutoMindr, some cars will have different needs. See below:
Time period between oil changes
Mileage period between oil changes
Windshield wiper size
Tire size
Preferred gas octane
Diagnostic Codes
Oil Type
Information for hybrids, electric cars, etc.
Maintenance -action IDs
Knowledge of Vehicle Customizations
In our example with Jeff, Jeff installed bigger wheels on his SUV. When he needs new tires, he will need to buy low-profile tires for his rims. AutoMindr needs to be able to store customizations and help with maintenance on customized parts. AutoMindr also recommends new parts like windshield wipers. Not all data needs to be in AutoMindr. Perhaps other sources exist that AutoMindr can port from. AutoMindr will need how to store enough information to at least map to this data though. Some examples:
replaced on a regular maintenance schedule such as windshield wipers, OR
after-market customizations such as larger wheels
Maintenance-action IDs
Service Center Profile
Service Center ID
Location
ID’s of all associated professional
Customer IDs that use the service center and their permissions (for example, a service center has read-access to Jeff's maintenance log, but read and write access to Bekkah's maintenance log).
Question-bank Table
This is the bank of quiz questions that quizzes are pulled from.
Quiz Question ID
Question (may eventually have two part questions)
Answer
Maintenance-type ID (corresponds to type such as tire tread)
Tutorial-bank
This is the bank of tutorials.
Tutorial ID
Tutorial (can include images, media, quizzes to test for understanding, and so on. This needs to be flexible).
Maintenance-type ID (corresponds to type such as tire tread)
Motivation-bank Table
Jeff remembers a time where he did not replace his worn-out tires in time and got into an accident on a rainy day. Jeff contributes this story and it shown to Bekkah when AutoMindr helps her recognize that she needs new tires. When Jeff uses AutoMindr and checks his tire pressure, he learns that by having the optimum tire pressure, mpg is improved. AutoMindr has both user-generated and "canned" motivations.
Maintenance-type ID (corresponds to type such as tire tread)
Canned motivations
User-generated motivation Stories (contains user ID to map back to permissions)
Jeff and Bekkah's Data
Bekkah is primary driver of her car. After using AutoMindr, Bekkah has after-market wipers installed on her car for better visibility. Bekkah is a secondary driver on her mom's car and her dad's SUV. Bekkah is buddies in AutoMindr with her mom and is mentored by her dad. Bekkah usually lives in her apartment near the university she attends, however, she still uses her parent's address sometimes. In June, Bekkah will be taking an internship out of state and plans to take her car with her. She will later return to her apartment.Jeff is Bekkah's dad. He mentors Bekkah in AutoMindr and is also a user. He is secondary driver on Bekkah's car and his wife's car. He is primary driver on his SUV. He is buddies with his wife. Jeff customized his SUV to have larger wheels than what comes standard. Jeff prefers to go to Al's Garage primarily because he really likes the work that Tricia does there. Jeff would like to give Tricia a separate rating different than Al's Garage.
Both Bekkah and Jeff will have the ability to view:
2.3.1 Vehicle History and Status
2.3.2 Driver History
Breakdown of Data Categories
User History
See 2.1 Profile for additional information regarding the profile information that needs to be stored and mapped to.Tutorial History
AutoMindr needs to know what tutorials a driver opts into or out of. AutoMindr also needs to map a tutorial to maintenance and car status. For example, Bekkah's learns she needs new tires with a tutorial. The tutorial guides her into changing her car's status to needing new tires. Eventually, she gets new tires and this maintenance item needs to be logged and the vehicle's status needs to changes.AutoMindr needs to store if a tutorial was or was not completed. Did user choose to ignore or attempt? At first, Bekkah was asked to check her tires but didn't have time. Later, Bekkah uses the tutorial. Jeff on the other hand, opts out of the tutorials. AutoMindr needs to store both the history and preferences.
The tutorial also need to map to what car status they might change (new tires for example). Status changes are usually also a maintenance action too.
Quiz History
AutoMindr gives quizzes. Quiz history needs to be stored so it can be viewed. This data might also be used to define user levels for example. Quizzes need to be mapped to the user taking them. The date and location is used to determine the most convienient time to offer quizzes to drivers.Vehicle
Profile
Status and Maintenance History
Status data and Maintenance data may be duplicated in the list below. This data may be combined in the backend. What is important though is that he car's current status must be accessible quickly and easily so AutoMindr can be intelligent enough to pick the right tutorials, quizzes, maintenance-action items (nag prompts), and so on. It is also important that the driver, mentor, or service professional be able to review the maintenance history. This history may be reviewed in whole or only one part of the history would be reviewed. For example, someone may just want to review the history of the transmission fluid.Status
Maintenance History
Knowledge of Vehicle Makes and Models
This data does not necessarily need to be stored in AutoMindr, but AutoMindr will need access this data. This data includes information that would come from a manual for a particular make, model, year, and class (for example 2002 Oldsmobile Alero GX). If this data is stored in AutoMindr, some cars will have different needs. See below:Knowledge of Vehicle Customizations
In our example with Jeff, Jeff installed bigger wheels on his SUV. When he needs new tires, he will need to buy low-profile tires for his rims. AutoMindr needs to be able to store customizations and help with maintenance on customized parts. AutoMindr also recommends new parts like windshield wipers. Not all data needs to be in AutoMindr. Perhaps other sources exist that AutoMindr can port from. AutoMindr will need how to store enough information to at least map to this data though. Some examples:Service Center Profile
Question-bank Table
This is the bank of quiz questions that quizzes are pulled from.Tutorial-bank
This is the bank of tutorials.Motivation-bank Table
Jeff remembers a time where he did not replace his worn-out tires in time and got into an accident on a rainy day. Jeff contributes this story and it shown to Bekkah when AutoMindr helps her recognize that she needs new tires. When Jeff uses AutoMindr and checks his tire pressure, he learns that by having the optimum tire pressure, mpg is improved. AutoMindr has both user-generated and "canned" motivations.